Create user module
With the Create User module, a user can be created for an e-mail print based on the sending e-mail address if no user is found under the sending e-mail address (see also E-MailPrint). Access data to the system (PIN or password) can be generated automatically and sent to the user at the sending e-mail address. The e-mail address is automatically used as the login name. If the user already exists, it remains unchanged.
The module cannot be used to create a user that was sent via a spooler by an unknown user (or an unknown login).

The module may occur only once in the workflow.

The module can be connected to all modules (this can result in nonsensical workflows).

Successful: This is the module that is executed if the user was created successfully.
Failed: The module that is to be executed if the user was not created successfully follows here.


The automatically created user can be given the rights below.
Field | Description |
---|---|
Print in color | The user is able to print in color. |
Copy in color | The user is able to copy in color. |
Choose own direct printer | The user can choose their own direct printer favorites in the WebClient, see Select favorites and direct printer. |
Own address book | The user has the possibility to maintain their own address book via the WebClient and use the entries on the device, see My address book. Without this right, the My Address Book area is not visible in the WebClient. |

The selected access data is automatically sent to the created user by e-mail (this is the sending e-mail address of the e-mail print). Pin code and password are generated in the minimum length and all allowed characters can occur, see also Define complexity of pin codes.
Field | Description |
---|---|
Create password | A password is automatically created and sent to the user. |
Create pin code | A pin code is automatically generated and sent to the user. |

The user to be created with limited validity will be created (after the validity expires, the user will be deleted automatically).
Field | Description |
---|---|
Type of validity limit | Specify whether the validity of the user should be limited:
After a validity limit has expired, the user will immediately no longer be able to log in to the system. The user is automatically deleted during a later test run (this is carried out when a service is started, for example). |
Validity period in days / months | This field appears if a validity in days or months was selected for the Type of validity limit. Depending on the type of validity limit, enter the number of days or months that may pass after the user's last login before the user can no longer log in and is then deleted (field Valid until is set automatically when the user logs in to the system). |


This notification is sent to the user if a password is to be generated automatically.
Field | Description |
---|---|
Notification active | Specify whether or not to send an e-mail for this event. If this setting is not available, the notification cannot be deactivated. |
Type of notification | The e-mails can be sent in HTML or text format. In some places a message can also be sent as a push notification with IQ4docs Messenger, see also IQ4docs Messenger. The length of push notifications may be limited depending on the operating system. |
Recipient | Specify one or more e-mail addresses (separated by semicolons) to which the e-mail should be sent. It is also possible to use the e-mail address stored with the user (%EMAIL%), see also Variables. If this field is not displayed, the e-mail notification automatically uses the e-mail address of the user executing the workflow (this field is not available for push messages). When testing the connection, the e-mail address of the user currently logged in to WebAdmin is then used. |
Sender | Specify an e-mail address to be used as the sender of the e-mail. This is also the address that is used when the recipient of the e-mail clicks on Reply in the e-mail program. It is also possible to use the e-mail address stored with the user (%EMAIL%), see also Variables; this can be useful for some events, since the user who has encountered the problem can be contacted by e-mail. If this field is not displayed, the e-mail notification automatically uses the e-mail address of the user executing the workflow (this field is not available for push messages). When testing the connection, the e-mail address of the user currently logged in to WebAdmin is then used. |
Language | Select the language in which the e-mails should be sent. |
Subject | Specify the desired text to be used as the e-mail subject. |
Message | Enter the desired message here. Depending on the type of notification, use plain text or HTML code here. If this field is not displayed, the text will be supplied in full from the message template. |
Send Test Notification sends a test message with the selected settings. For the test, the user data of the user who is currently logged in to the WebAdmin are used (if you make changes to the data of this user, you must log out and log in again in order for this data to be loaded). It might not be possible to resolve variables at this point because the workflow was not actually executed. When testing, also note the settings for the recipient and sender.
Load Defaults fills the fields for Recipient, Sender, Language and Subject with default settings - any values that may have been entered are replaced.

This notification is sent to the user if a pin code is to be generated automatically.
Field | Description |
---|---|
Notification active | Specify whether or not to send an e-mail for this event. If this setting is not available, the notification cannot be deactivated. |
Type of notification | The e-mails can be sent in HTML or text format. In some places a message can also be sent as a push notification with IQ4docs Messenger, see also IQ4docs Messenger. The length of push notifications may be limited depending on the operating system. |
Recipient | Specify one or more e-mail addresses (separated by semicolons) to which the e-mail should be sent. It is also possible to use the e-mail address stored with the user (%EMAIL%), see also Variables. If this field is not displayed, the e-mail notification automatically uses the e-mail address of the user executing the workflow (this field is not available for push messages). When testing the connection, the e-mail address of the user currently logged in to WebAdmin is then used. |
Sender | Specify an e-mail address to be used as the sender of the e-mail. This is also the address that is used when the recipient of the e-mail clicks on Reply in the e-mail program. It is also possible to use the e-mail address stored with the user (%EMAIL%), see also Variables; this can be useful for some events, since the user who has encountered the problem can be contacted by e-mail. If this field is not displayed, the e-mail notification automatically uses the e-mail address of the user executing the workflow (this field is not available for push messages). When testing the connection, the e-mail address of the user currently logged in to WebAdmin is then used. |
Language | Select the language in which the e-mails should be sent. |
Subject | Specify the desired text to be used as the e-mail subject. |
Message | Enter the desired message here. Depending on the type of notification, use plain text or HTML code here. If this field is not displayed, the text will be supplied in full from the message template. |
Send Test Notification sends a test message with the selected settings. For the test, the user data of the user who is currently logged in to the WebAdmin are used (if you make changes to the data of this user, you must log out and log in again in order for this data to be loaded). It might not be possible to resolve variables at this point because the workflow was not actually executed. When testing, also note the settings for the recipient and sender.
Load Defaults fills the fields for Recipient, Sender, Language and Subject with default settings - any values that may have been entered are replaced.

This notification is sent to the sender if the user could not be generated automatically.
Field | Description |
---|---|
Notification active | Specify whether or not to send an e-mail for this event. If this setting is not available, the notification cannot be deactivated. |
Type of notification | The e-mails can be sent in HTML or text format. In some places a message can also be sent as a push notification with IQ4docs Messenger, see also IQ4docs Messenger. The length of push notifications may be limited depending on the operating system. |
Recipient | Specify one or more e-mail addresses (separated by semicolons) to which the e-mail should be sent. It is also possible to use the e-mail address stored with the user (%EMAIL%), see also Variables. If this field is not displayed, the e-mail notification automatically uses the e-mail address of the user executing the workflow (this field is not available for push messages). When testing the connection, the e-mail address of the user currently logged in to WebAdmin is then used. |
Sender | Specify an e-mail address to be used as the sender of the e-mail. This is also the address that is used when the recipient of the e-mail clicks on Reply in the e-mail program. It is also possible to use the e-mail address stored with the user (%EMAIL%), see also Variables; this can be useful for some events, since the user who has encountered the problem can be contacted by e-mail. If this field is not displayed, the e-mail notification automatically uses the e-mail address of the user executing the workflow (this field is not available for push messages). When testing the connection, the e-mail address of the user currently logged in to WebAdmin is then used. |
Language | Select the language in which the e-mails should be sent. |
Subject | Specify the desired text to be used as the e-mail subject. |
Message | Enter the desired message here. Depending on the type of notification, use plain text or HTML code here. If this field is not displayed, the text will be supplied in full from the message template. |
Send Test Notification sends a test message with the selected settings. For the test, the user data of the user who is currently logged in to the WebAdmin are used (if you make changes to the data of this user, you must log out and log in again in order for this data to be loaded). It might not be possible to resolve variables at this point because the workflow was not actually executed. When testing, also note the settings for the recipient and sender.
Load Defaults fills the fields for Recipient, Sender, Language and Subject with default settings - any values that may have been entered are replaced.


The UserService reads the user information from the database. If users are imported, it reads the data e.g. from a directory service into the IQ4docs database. Its log file is Logs\UserService.log.